Sourced from coverage's changelog.

Change history for Coverage.py

Unreleased

• fail_under values more than 100 are reported as errors. Thanks to Mike Fiedler for closing issue 746.
• The "missing" values in the text output are now sorted by line number, so that missing branches are reported near the other lines they affect. The values used to show all missing lines, and then all missing branches.
• Line numbers in the HTML report now align properly with source lines, even when Chrome's minimum font size is set, fixing issue 748. Thanks Wen Ye.

Version 5.0a4 --- 2018-11-25

• You can specify the command line to run your program with the [run] command_line configuration setting. issue 695.
• Coverage will create directories as needed for the data file if they don't exist, closing issue 721.
• The coverage run command has always adjusted the first entry in sys.path, to properly emulate how Python runs your program. Now this adjustment is skipped if sys.path[0] is already different than Python's default. This fixes issue 715.
• Improvements to context support:
  • The "no such table: meta" error is fixed.: issue 716.
  • Combining data files now goes much faster.
• Python 3.8 (as of today!) passes all tests.

Version 5.0a3 --- 2018-10-06

• Context support: static contexts let you specify a label for a coverage run, which is recorded in the data, and retained when you combine files. See contexts for more information.
• Dynamic contexts: specifying [run] dynamic_context = test_function in the config file will record the test function name as a dynamic context during execution. This is the core of "Who Tests What" (issue 170). Things to note:
  • There is no reporting support yet. Use SQLite to query the .coverage file for information. Ideas are welcome about how reporting could be extended to use this data.
  • There's a noticeable slow-down before any test is run.
  • Data files will now be roughly N times larger, where N is the number of tests you have. Combining data files is therefore also N times slower.
  • No other values for dynamic_context are recognized yet. Let me know what else would be useful. I'd like to use a pytest plugin to get better information directly from pytest, for example.
• Environment variable substitution in configuration files now supports two syntaxes for controlling the behavior of undefined variables: if VARNAME is not defined, ${VARNAME?} will raise an error, and ${VARNAME-default value} will use "default value".
• Partial support for Python 3.8, which has not yet released an alpha. Fixes issue 707 and issue 714.

Version 5.0a2 --- 2018-09-03

• Coverage's data storage has changed. In version 4.x, .coverage files were basically JSON. Now, they are SQLite databases. This means the data file can be created earlier than it used to. A large amount of code was refactored to support this change.
  • Because the data file is created differently than previous releases, you may need parallel=true where you didn't before.
  • The old data format is still available (for now) by setting the environment variable COVERAGE_STORAGE=json. Please tell me if you think you need to keep the JSON format.
  • The database schema is guaranteed to change in the future, to support new features. I'm looking for opinions about making the schema part of the public API to coverage.py or not.
• Development moved from Bitbucket to GitHub.
• HTML files no longer have trailing and extra whitespace.
• The sort order in the HTML report is stored in local storage rather than cookies, closing issue 611. Thanks, Federico Bond.
• pickle2json, for converting v3 data files to v4 data files, has been removed.

Version 5.0a1 --- 2018-06-05

• Coverage.py no longer supports Python 2.6 or 3.3.
• The location of the configuration file can now be specified with a COVERAGE_RCFILE environment variable, as requested in issue 650.

... (truncated)

• See full diff in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.